-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix remote constants. #7689
Fix remote constants. #7689
Conversation
Do not know how to create a good simple test. |
Is this related to #7247 , e.g. should we prevent pushing down non-deterministic functions to remote server? |
@akuzm I think it is strange to use functions like |
uptime is already marked as non-deterministic, while version is deterministic. Maybe we should mark it as deterministic in scope of query, and only ship deterministic functions to replicas. |
Yes, it seems reasonable. |
4b6e8bb
to
0ba523a
Compare
Fix remote constants. (cherry picked from commit 2233660)
Fix remote constants. (cherry picked from commit 2233660)
Fix remote constants. (cherry picked from commit 2233660)
Fix remote constants. (cherry picked from commit 2233660)
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Changelog category (leave one):
Changelog entry (up to few sentences, not needed for non-significant PRs):
Fix possible incorrect result for constant functions from remote servers. It happened for queries with functions like
version()
,uptime()
, etc. which returns different constant values for different servers. #7666Detailed description (optional):
Get constant values from remote source in RemoteBlockInputStream.